The dynamic blocklist is applied even if the third party module blocking was disabled via the DisableThirdPartyModuleBlocking policy
Categories
(Firefox :: Enterprise Policies, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr102 | --- | unaffected |
firefox108 | --- | unaffected |
firefox109 | --- | unaffected |
firefox110 | --- | affected |
People
(Reporter: emilghitta, Assigned: gstoll)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
6.05 MB,
image/gif
|
Details |
Found in
- Firefox 110.0a1 (Build Id: 20230102165835)
Affected versions
- Firefox 110.0a1 (Build Id: 20230102165835)
Tested platforms
- Affected platforms: Windows 10 64bit
Preconditions
- Have Google Drive for desktop installed (https://www.google.com/drive/download/)
- Launch Firefox.
- Block the drivefsext.dll via the about:third-party page.
- Restart Firefox.
Steps to reproduce
- Disable the user-driven DLL blocking by using the following policy inside the policies.json file:
{ "policies": { "DisableThirdPartyModuleBlocking": true } }
- Restart Firefox.
- Press ALT + F and select "Open File".
- Access the about:third-party page and inspect the drivefsext.dll.
Expected result
- Step 3: The Google Drive entries have a little cloud overlay displayed.
- Step 4: The drivefsext.dll has the status of Loaded.
Actual result
- Step 3: No cloud overlay is displayed for the Google Drive entries.
- Step 4: The drivefsext.dll has the status of Blocked.
Regression range
- This is not a regression.
Assignee | ||
Updated•2 years ago
|
Assignee | ||
Comment 1•2 years ago
|
||
The problem is that InitializeDllBlocklistOOPFromLauncher()
calls PolicyCheckBoolean(L"DisableThirdPartyModuleBlocking")
to see if the blocklist is disabled, but that just checks the registry key. (the about:third-party page itself does seem to work correctly) I'm not sure if we should be reading the JSON file to look for this specifically...
Comment 2•2 years ago
|
||
So this is going to be a limitation.
You can only turn off the blocklist via GPO, not policies.json. This is similar to a few other Windows specific policies.
Sorry, I should have caught that when this report was opened.
Reporter | ||
Comment 3•2 years ago
|
||
Thanks for the info! I was not aware of that :D.
I'm going to update our tests & will apply this policy directly via regedit or GPO instead.
My guess is that we can mark this ticket as wontfix then?
Comment 4•2 years ago
|
||
Thanks for the info! I was not aware of that :D.
I should have caught that.
My guess is that we can mark this ticket as wontfix then?
yep
Description
•